-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plot editor tab sizing policies #6043
Conversation
Define metadata per client instance Filter plots from action that don't support sizing
E2E Tests 🚀 |
The unit test needs a rewrite to check that a plot client sends an event for sizing policy changes. I also think the plots service doesn't need to the event anymore. |
Fix unit test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, we definitely need some better affordances here but I see that work is still scheduled!
Release Notes
Addresses #5522 and #4358
Each plot client has their own metadata that now includes the sizing policy. Each plot can, whether it is in an editor tab or the view, independently set a sizing policy that will be restored on reload.
Adds an action that can switch between sizing policies for the selected plot. The action only shows the options that would be available from the sizing policy menu button in the Plots view. A custom sizing policy can only be set if there already is one set in the Plots view. It cannot be altered from the action.
Restored editors might not restore to the same editor group if there are multiple. I can follow up with adding that to the plot metadata so it can be restored to the same location. The editor order may also not be the same but I think we can live with that.
Finally, it also needs another update later to add the action to the editor toolbar but that will need more work to allow a menu style button.
Screen.Recording.2025-01-17.at.4.27.23.PM.mov
New Features
Change Plot Sizing Policy
Bug Fixes
QA Notes
This is still hidden behind an experimental setting.